Repository navigation
project(orchestration-primitives): FIX-2071 wraps — the renames landed; four calls decided once - #4254
Conversation
…d; four calls decided once FIX-2071's row goes to done (seven children and closure #4244 merged, Linear Done Oct 30) and its arc bar closes. Status re-derived from Linear: FIX-2070 and FIX-2092 are in flight. The now line moves to Oct 30. Decided once, from FIX-2071: D1 (a renamed name is refused, never an alias), ER-2 (every rename ships a committed codemod), ER-3 (RETIRED rows only grow), and D2's rename table as the vocabulary contract. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NczDiDaAHdCicsHDpBceid
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Second look: PR #4254Verdict: approach is right, ready after two small stale-text fixes. No refactor warranted. This is a derived-status refresh of a project spec (docs/figures only, no code), so the leaner path is already taken. It re-derives from Linear and adds four decision rows, and it leaves the outcome, PD-1 to PD-3 and the rules alone. Checked and fine
Fix before merge (stale text this PR makes wrong)
Nits
Architecture note (not for this PR) Generated by Claude Code |
|
Process guards is red because of where this PR comes from, not what it changes. There is no fix inside this PR. Moving the files would defeat the PR. Changing the guard is out of scope for a status update. The same commit (c28c289) passes the guard if it is pushed straight to Generated by Claude Code |
There was a problem hiding this comment.
/simplify review
Verdict: Approve. This is a spec-only project refresh after FIX-2071 wrapped, and it follows the same shape as the FIX-2058 wrap (#684fbbc): mirror binding decisions into DECISIONS.md, add a What FIX-2071 left open section on PLAN.md, bump the live epics table and kill line on SPEC.md, and hand-update figures/arc.svg. That four-surface sync is deliberate for this project-spec set, not accidental scope creep in this PR.
Did the approach go too far? The underlying FIX-2071 epic was heavy (codemods, vocabulary, refusal semantics). This PR mostly records outcomes. The one place I’d consider a lighter alternative (optional, not blocking) is how much FIX-2071 process lands in the project decided once table versus staying in specs/epics/FIX-2071/ with a link — see inline on codemod / RETIRED rows.
Cleaner alternatives considered (for future refreshes, not a rewrite of this PR):
| Idea | Tradeoff |
|---|---|
Single canonical status — treat SPEC.md → The epics as source of truth; shorten arc aria-label and keep PLAN on ordering/hand-offs only |
Less duplicate prose on every “now line” bump; arc becomes more schematic |
Generate arc.svg from a small data file (dates + state per lane) |
Up-front script vs repeated magic coordinates (896.4, bar widths); no third-party package required, but repo today is hand-maintained SVG across project figures |
| Trim the seven-child PR laundry list in PLAN to match FIX-2056/2058 “left open” sections (closure + carried-forward table only) | History stays on epic spec / Linear; project PLAN stays scannable |
Skipped as out of scope / uncertain: Regenerating mermaid styling for in-flight epics (edges still read D2070 → D2071 as strict sequencing while prose correctly says 2071 wrapped before 2070’s closure). Worth a follow-up pass if the diagram is meant to track partial deps, not just wrap order. Terminology in The read still says “hold” post-rename — likely a separate terminology sync, not required for this status refresh.
Performance: Static SVG, no SMIL; ~828-char aria-label is maintainability/a11y verbosity, not runtime cost.
No code changes requested from this automation run.
Sent by Cursor Automation: Review For Best Approach
…X-2071 consumes FIX-2070's builds Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NczDiDaAHdCicsHDpBceid
There was a problem hiding this comment.
Code Snob. The wrap note is longer than the contract it carries.
PLAN.md lists seven merged child PRs, then a two-row table whose rows both point at lessons draft #4245, then a sentence that the four decided-once rows live in DECISIONS.md. The epics table already links the closure (#4244) and that draft. The order blurb also restates that FIX-2070 and FIX-2092 are in flight.
Cut those. Keep the closure citation, the two owner asks, and F1–F7. Leave the four decision rows, the arc, and the epics table alone.
Shown on draft #4256 (poc/shorter-fix-2071-left-open, c7fff8495). Spec-figure checks still pass. PLAN 1260 → 1216 words.
That draft does not merge. Agent on this PR: fold the subtraction, then close the POC unmerged after this one lands.
Sent by Cursor Automation: Code Snob
…e closure and lessons once Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NczDiDaAHdCicsHDpBceid
|
Pushed 747a152, which folds both Cursor reviews. Process guards will stay red for the branch-name reason above until the owner decides the route. The Linear mirror now matches 747a152. Generated by Claude Code |
7927905
into
project/orchestration-primitives


Requested by Jake · project thread
The wrap update for FIX-2071 (coordination renames) on the Orchestration Primitives project-spec. It targets
project/orchestration-primitives, notmain. Merging it lands the update on the never-merged project PR #3102.What moved
figures/arc.svg). FIX-2071's bar closes (Oct 21 to Oct 30). FIX-2070 and FIX-2092 get in-flight bars. The now line moves to Oct 30. Rendered and checked in light and dark.scripts/codemod/.RETIREDrows ingoals/vocabulary/one-word-per-thingonly ever grow.specs/epics/FIX-2071/renames.mdis the vocabulary contract.Outcome, PD-1 to PD-3 and the rules are unchanged.
Evidence (checked on
mainat 863a0e1)specs/epics/FIX-2071/DECISIONS.md(D1, D2, ER-2, ER-3) onmain.scripts/codemod/has the codemods.BUSINESS-RULES.mdprints nothing.The Linear project's
contentis re-mirrored from this head.Generated by Claude Code